feat(ByteTrack): Allow ByteTrack to track detection without class ids #1618
Conversation
Kadermiyanyedi
force-pushed
the
allow-bytetrack-detection-without-class-ids
branch
from
c0de341 to
dbd4aa7
Compare
|
Hey @Kadermiyanyedi 👋 Did you try checking what happens with the Is that something you'd have time for? |
LinasKo
added
the
hacktoberfest-accepted
|
I suggested a special value other than However, I'll take an unconventional approach and merge the PR, in hopes of finding a way to remove the need for classes entirely. If that fails, I'll come back and change the special value to something else. Thank you @Kadermiyanyedi! Expect to see this in the next supervision release 😉 |
|
@LinasKo Hi, due to the busy schedule, I missed your comment on the PR and forgot to reply—sorry about that. I tested your suggestion and confirmed that class IDs are not necessary; it works without them. I’m opening a PR for this right away. Would it be possible to revert the PR we merged? |
|
✅ Reverted |
LinasKo
removed
the
hacktoberfest-accepted
Description:
This PR modifies ByteTrack to handle detections that do not include a class_id, improving the flexibility of the tracking algorithm. In cases where models don’t return a class_id, ByteTrack will now assign a default internal ID to ensure continued tracking.
Key Changes:
Default class_id Assignment:
This ensures that ByteTrack works seamlessly with models that do not provide class_id, without breaking existing functionality.
You can test the functionality with the provided Colab Notebook which demonstrates ByteTrack handling cases with and without class_id.
#1582